Third Party Paywall Authentication System

ABSTRACT

The present technology provides a less burdensome mechanism to bring media items owned or licensed in the physical world into an account hosted by an electronic media provider. A specific use case deals with magazine subscriptions wherein the electronic media provider can send entity identifying information to a publisher clearinghouse that has subscription data for many different magazines. If the entity information sufficiently matches subscription information, the clearinghouse sends back data identifying magazines for which the entity is entitled to a digital copy, and these magazines become available to the user through the electronic media provider.

BACKGROUND

1. Technical Field

The present disclosure relates to digital media items and morespecifically to automatically providing access to digital versions ofnon-digital media subscribed to by a user.

2. Introduction

Many users have existing subscriptions to non-digital media such aspublications including magazines, newspapers, movies, music, etc. anddesire the ability to view these publications in digital format using ahandheld device or computer system. Oftentimes, a publisher will requirea user to visit the publisher's website to authenticate theirsubscription with the non-digital media to access the content in digitalversion that they have already paid for in non-digital media. Theauthentication process may prove burdensome and time consuming as itoften requires the user to enter several pieces of authenticatinginformation at the publisher website including the user's name,telephone number, address, date of birth, last few digits of thenon-digital media barcode, credit card used to purchase the non-digitalmedia, etc. If the user subscribes to several non-digital media, theuser may be unmotivated to access digital versions of non-digital mediathey already subscribe to due to the amount of time required for theauthentication process.

Media distribution platforms offer digital versions of publications frompublishers that also offer printed versions of the publication. To avoidauthenticating subscriptions individually for all the publishers theuser is subscribed to, some users prefer to purchase digitalsubscriptions from publishers on a media distribution platform. However,in some cases, a user can be charged a second time when the userpurchasing digital versions of the publications already subscribes tothe same publisher in non-digital media.

Accordingly, there is a need for systems, methods, and computer readablemedia that allow users to automatically access digital versions ofnon-digital media they subscribe to with minimal effort without doublecharging for the digital versions.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for automatically providing access to digital versions ofnon-digital media subscribed to by a user. Some embodiments of thepresent technology involve receiving subscription data from publishers,the subscription data relating to multiple third-party subscribers. Insome embodiments third-party subscribers are matched with users of amedia distribution platform which grants those users with a digitalsubscription to their content.

In some embodiments a media distribution platform will attempt toautomatically authenticate a user's subscriptions to publications byaccessing subscription data available from publishers and performing adata match between the subscription data and media distribution platformuser profile data. Upon completion of a successful data match betweenthe subscription data and user profile data, a user can be provided withdigital access to all the content they subscribe to in printed form on amedia distribution platform. The media distribution platform can utilizea universal reader to display and view multiple publications fromvarious publishers.

In some cases publishers might not agree to provide a media distributionplatform with subscription data. In this scenario, a media distributionplatform can automatically request a user's identification informationfrom a user profile database, thus requiring no input from a user. Theidentification information can in turn be sent to a publisher and, ifthe publisher recognizes it, provide the user with an access token for agiven subscription. In some embodiments, the access token for a givensubscription will be included whenever the user receives digital contentrelating to the subscription from the publisher. This enables thepublisher to refuse the access token whenever the subscription isexpired or cancelled. Once access to the digital version of thepublication is granted, the media distribution platform can utilize auniversal reader to display and view multiple publications from variouspublishers.

According to some embodiments there are some situations whereautomatically authenticating a user's subscription to publications mightfail. In this scenario, a media distribution platform can present a userinterface within the media distribution platform containing fields apublisher has requested for a user to populate to verify a user'ssubscription to publications. The user's input can be sent to thepublisher and, if the publisher recognizes it, the publisher can providean access token for a given subscription. Once access to the digitalversion of the publication is granted, the media distribution platformcan utilize a universal reader to display and view multiple publicationsfrom various publishers.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features of the disclosure can be obtained, a moreparticular description of the principles briefly described above will berendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only exemplary embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 illustrates a general purpose computing environment in whichmultiple computing devices can be configured to communicate with eachother to automatically provide access to digital versions of non-digitalmedia subscribed to by a user;

FIG. 2 illustrates a method of automatically authenticating a user'ssubscription to non-digital media where publishers have shared theirsubscription data with a media distribution platform;

FIG. 3 illustrates a method of automatically authenticating a user'ssubscription to non-digital media where publishers subscription data isprivate;

FIG. 4 illustrates a method of automatically providing access to digitalversions of non-digital media a user subscribes to where thesubscription data is available to the media distribution platform;

FIG. 5 illustrates a method of automatically providing access to digitalversions of non-digital media a user subscribes to where thesubscription data is private;

FIG. 6 illustrates a method of providing digital access to non-digitalmedia subscribed to by a user where the subscription data is availableto the media distribution platform;

FIG. 7 illustrates a method of providing access to digital versions ofnon-digital media a user subscribes to where the subscription data isprivate;

FIG. 8 illustrates an example flowchart of how a user's subscription toa non-digital media is authenticated and how digital versions of thenon-digital media are a provided;

FIG. 9A illustrates a conventional bus computing system architectureaccording to some embodiments of the present technology; and

FIG. 9B illustrates a computer system having a chipset architectureaccording to some embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationscan be used without parting from the spirit and scope of the disclosure.

As explained above, there is a need for systems, methods, and computerreadable media that allow users to automatically access digital versionsof non-digital media they subscribe to with minimal effort withoutdouble charging for the digital versions. Some embodiments of thepresent technology involve receiving subscription data from publishers,the subscription data relating to multiple third-party subscribers. Insome embodiments third-party subscribers are matched with users of amedia distribution platform which grants those users with a digitalsubscription to their content.

In some embodiments, a media distribution platform will attempt toautomatically authenticate a user's subscriptions to publications byaccessing subscription data available from publishers and performing adata match between the subscription data and media distribution platformuser profile data. Upon completion of a successful data match betweenthe subscription data and user profile data, a user can be provided withdigital access to all the content they subscribe to in printed form on amedia distribution platform. The media distribution platform can utilizea universal reader to display and view multiple publications fromvarious publishers.

In some cases publishers might not agree to provide a media distributionplatform with subscription data. In this scenario, a media distributionplatform can automatically request a user's identification informationfrom a user profile database requiring no input from a user. Theidentification information can in turn be sent to a publisher and, ifthe publisher recognizes it, the publisher will provide the user with anaccess token for a given subscription. In some embodiments, the accesstoken for a given subscription will be included whenever the userreceives digital, media relating to the subscription from the publisher.This enables the publisher to refuse the access token if thesubscription has expired or is cancelled. Once access to the digitalversion of the publication is granted, the media distribution platformcan utilize a universal reader to display and view multiple publicationsfrom various publishers.

According to some embodiments there are some situations whereautomatically authenticating a user's subscription to publications mightfail. In this scenario, a media distribution platform can present a userinterface within the media distribution platform containing fields apublisher has requested for a user to populate to verify a user'ssubscription to publications. The users input can be sent to thepublisher and, if the publisher recognizes it, the publisher can providean access token for a given subscription. This access token can beincluded with digital content relating to the subscription from thepublisher that is sent to the user. This enables the publisher to refusethe access token whenever the subscription has expired or is cancelled.Once access to the digital version of the publication is granted, themedia distribution platform can utilize a universal reader to displayand view multiple publications from various publishers.

FIG. 1 illustrates a system configuration 100 in which multiplecomputing devices can be configured to authenticate a user'ssubscription to non-digital media and provide access to digital versionsof the non-digital media in a media distribution platform 115 on aclient device 105. Although one client device 105 is depicted, it shouldbe understood that multiple client devices can be associated with aparticular user. Some non-limiting examples of non-digital media caninclude periodicals such as magazines, newspapers, brochures, etc. Insome embodiments, other physical media can be a “non-digital media,”e.g., CDs, DVDs, Blu-Ray disc, etc. An example of a media distributionplatform 115 is ITUNES, available from Apple Inc. of Cupertino, Calif.The media distribution platform can be configured to store, sell, rent,stream any type of digital media product such as music, movies,television shows, user-generated videos, digital books, podcasts,applications, magazines, newspapers, periodicals, photos, artwork, etc.

According to some embodiments, the current technology can be configuredto authenticate a user's subscription to digital publications offered ona publisher's website and provide access to the digital publications ina media distribution platform 115 on a client device 105. Providingaccess to the user's subscription to digital publications offered onmultiple publishers' websites allows for efficient access to the user'sdigital publications on one common platform. This eliminates the needfor the user to log into multiple publishers' websites in order toaccess digital subscription content from a plurality of publishers.

In some embodiments, a media distribution platform can make multiplepublications offered by multiple publishers available for viewing usinga universal reader. In some cases, publications accessed directly from apublisher's website can require a reader specific to that website toview the publication. Requiring a user to visit each publisher'sindependent website to view the publications offered by that publishercan prove time consuming and burdensome. By contrast, the mediadistribution platform having the capability to provide a plurality ofpublications from a plurality of publishers in one location using oneuniversal reader allows a user to view publications they subscribe towith ease.

According to some embodiments, a user can authenticate theirsubscriptions to non-digital media by providing one input into a mediadistribution platform, i.e., a click of a mouse, an input on a touchscreen of a graphical user interface of a mobile device, or one inputinto a media distribution platform, etc. In some embodiments, uponsigning into a new product a user can be presented with a series ofgreetings such as “Welcome to the new product!,” “Do you have anyexisting print subscriptions that you would like to receive a digitalversion of?,” “Sign in with your ID and perform a check.” Uponsuccessful verification of the user's subscription to the non-digitalmedia, the product can present to the user a success dialog such as “Youhave access to Newsweek, Time and Sports Illustrated.”

Authenticating a user's subscription to non-digital media with one clickof a mouse, one input on a touch screen of a graphical user interface ofa mobile device, or one input into a media distribution platform canoccur under multiple conditions. In some embodiments, a clearinghousedatabase 155 possesses a large majority of subscribers to a plurality ofpublishers P1, P2, P3, . . . P_(n). A Subscriber Server 180 can accessthe clearinghouse database 155 to retrieve subscription data associatedwith a plurality of publishers P1, P2, P3, . . . P_(n). In otherembodiments publishers have access to an application program interface(API) 160 for a Subscriber Server 180. Using API 160, the publishers cansubmit subscription data to the Subscriber Server 1 180. For instance P1Server 165 (Publisher 1), P2 Server 170 (Publisher 2), and P3 Server 175(Publisher 3) can utilize API 160 and communication network 110 to feedthe Subscriber Server 180 with their subscription data. In someinstances, the API can receive subscription data directly fromclearinghouse database 155. In some embodiments the Subscriber Server180 is separate from the media distribution platform server 125. Inother embodiments, Subscriber Server 180 is contained within the MediaDistribution Platform Server.

Providing the Subscriber Server 180 with subscription data from theclearinghouse database 155 or from API 160, which can receivesubscription data directly from publishers, enables the SubscriberServer 180 to match third-party subscribers to media distributionplatform users and automatically grant those users with a digitalsubscription to their content. Media distribution platform server 125can consist of a user profile database 145 which contains the mediadistribution platform user profile data. Data matching module 135matches third-party subscribers provided in the subscription data tomedia distribution platform users. Some non-limiting examples of datathat the data matching module 135 utilizes to perform the data matchincludes a user's name, maiden name, home addresses, business addresses,mailing addresses, email addresses, date of birth, etc.

Digital version database 140 can contain digital versions of non-digitalmedia from a plurality of publishers. Digital version database 140 canprovide digital versions of non-digital media a user subscribes to uponsuccessful completion of a data match. In some embodiments, a user canaccess the digital versions automatically granted to the user on aclient device 105 utilizing a client application of the mediadistribution platform.

Enabling the Subscriber Server 180 to authenticate a user's subscriptionto their printed content and automatically grant users with a digitalsubscription is the ideal scenario because it requires no input from theuser. The user simply has access to all their content on first launch ofthe product.

According to some embodiments, there are some situations whereautomatically authenticating a user's subscription to publications mightfail. In this scenario, a media distribution platform can present a userinterface within the media distribution platform containing fieldscorresponding to the subscription data available on the mediadistribution platform server. The users input can be matched against thesubscription data and, if successful, provide digital access to thenon-digital media subscribed to by the user. Once access to the digitalversion of the publication is granted, the media distribution platformcan utilize a universal reader to display and view multiple publicationsfrom various publishers.

However, in some instances a publisher might be unwilling to providetheir subscription data to the clearinghouse database 155, the API 160,or the Subscriber Server 180. Under these circumstances a user'ssubscription to non-digital media must be authenticated utilizing analternate approach. When a user claims to be an existing subscriber of anon-digital media from a publisher, the media distribution platformserver will start by trying to validate their subscription data behindthe scenes without requiring any input by the user. In some embodiments,a client application will request the user's billing address from themedia distribution platform server 125 and send it to the publisher. Ifthe publisher recognizes it, the publisher will in turn provide theclient with an access token. Access token module 130 can store theaccess token for a given subscription associated with a user. In someembodiments, the access token for a given subscription will be includedwhenever the user receives digital content relating to the subscriptionfrom the publisher. This enables the publisher to refuse the accesstoken whenever the subscription is expired or cancelled. Once access tothe digital version of the publication is granted, the mediadistribution platform can utilize a universal reader to display and viewmultiple publications from various publishers.

Although the access token module 130 is illustrated as a part of themedia distribution platform server 125, this is just one possibleembodiment and is not meant to be limiting. For example, the accesstoken module can be contained within the client device 105.

According to some embodiments there are some situations whereautomatically authenticating a user's subscription to publications mightfail. In this scenario, a media distribution platform can present a userinterface within the media distribution platform containing fields apublisher has requested for a user to populate to verify a user'ssubscription to publications. The user's input can be sent to thepublisher, and if the publisher recognizes it, the publisher can providean access token for a given subscription. The access token can beincluded whenever the user receives digital content relating to thesubscription from the publisher. This enables the publisher to refusethe access token if the subscription has expired or is cancelled. Onceaccess to the digital version of the publication is granted, the mediadistribution platform can utilize a universal reader to display and viewmultiple publications from various publishers.

To facilitate authenticating a user's subscription to non-digital mediaand automatically granting those users with a digital subscription totheir content, multiple computing devices can be connected to acommunication network 110 and configured to communicate with each otherthrough use of the communication network 110. The communication network110 can be any type of network, including a local area network (“LAN”),such as an intranet, a wide area network (“WAN”), such as the internet,or any combination thereof. Further, the communication network 110 canbe a public network, a private network, or a combination thereof. Thecommunication network 110 can also be implemented using any type ortypes of physical media, including wired communication paths andwireless communication paths associated with one or more serviceproviders. Additionally, the communication network 110 can be configuredto support the transmission of messages formatted using a variety ofprotocols.

A computing device can be any type of general computing device capableof network communication with other computing devices. For example, thecomputing device can be a personal computing device such as a desktop orworkstation, a business server, or a portable computing device, such asa laptop, smart phone, or tablet personal computer. The computing devicecan include some or all of the features, components, and peripherals ofcomputing device 900 of FIG. 9A.

To facilitate communication with other computing devices, the computingdevice can also include a communication interface configured to receivea communication, such as a request, data, etc., from another computingdevice in network communication with the computing device and pass thecommunication along to an appropriate module running on the computingdevice. The communication interface can also be configured to send acommunication to another computing device in network communication withthe computing device.

As illustrated, a client device 105 can be configured to communicatewith a media distribution platform server 125 to provide a mediadistribution platform on the client device 105. For example, a mediadistribution platform application 115 running on the client device 105can be configured to communicate with a digital version module 195 onthe media distribution platform server 125 to request, receive andperform digital versions of non-digital media a user subscribes togranted to the user.

Although the digital version database 140 and user profile database 145are illustrated separately, this is just one possible embodiment and isnot meant to be limiting. In some embodiments, the databases can becombined as one database or any other possible combination.

Alternatively, in some embodiments, the multiple databases can be hostedon separate computing devices and the digital version module 195 can beconfigured to communicate with the various computing devices to providethe digital versions to a user.

In some embodiments, the digital version module 195 can be configured totransmit the digital versions granted to a user to the client device 105where the digital versions can be presented by the media distributionplatform application 115. For example, the media distribution platformserver 125 can be in continuous communication with the mediadistribution platform application 115 to transmit the digital versionssubscribed to by a user to the media distribution platform application115.

In some embodiments, the media distribution server 125 can be configuredto transmit the digital versions subscribed to by a user to the clientdevice 105 in segments. For example, the digital version module 195 canbe configured to communicate with the client device to transmit the mostcurrent digital versions subscribed to by a user which can be stored onthe client device 105 and presented by the media distribution platformapplication 115. For example, the client device 105 can include adigital version database 190 configured to store the received digitalversions of non-digital media from a plurality of publishers and themedia distribution platform application 115 can be configured tocommunicate with the digital version database 190 to retrieve the storeddigital versions. In this type embodiment, the digital version module195 can be configured to periodically update the client device 105 bytransmitting digital versions subscribed to by a user.

In some embodiments, the digital versions of non-digital mediasubscribed to by a user can be assembled at the client device 105 ratherthan at the media distribution platform server 125. For example, thedigital version module 195 can be running on the client device 105 andcan be configured to request digital versions of non-digital mediasubscribed to by a user from the media distribution platform server 125,or any other computing device. The received digital versions ofnon-digital media subscribed to by a user can be stored in the digitalversion database 190 and the digital version module 195 can beconfigured to communicate with the digital version database 190 toretrieve the stored digital versions and to assemble the digitalversions for viewing. In this type of embodiment, the media distributionapplication 115 running on the client device 105 can be configured toperiodically request further digital versions to be delivered to theclient device.

The digital version module 195 can be configured to assemble the digitalversions based upon digital version assembly rules. The digital versionassembly rules can dictate which digital versions should be selected aswell as the sequential order in which they should be presented by themedia player application 115.

FIG. 2 illustrates a method of automatically authenticating a user'ssubscription to non-digital media where publishers have shared theirsubscription data with a media distribution platform. In some instances,publishers are willing to share their subscription data with a mediadistribution platform which allows the media distribution platform toauthenticate a user's subscriptions by performing a data match.

The method begins by Publisher 210 sending a request to SubscriberServer 220 to either create a new user subscription or delete anexisting user subscription. In some embodiments, the request containsthird-party subscriber subscription data. Some non-limiting examples ofsubscription data are the subscriber's name, maiden name, homeaddresses, business addresses, mailing addresses, email addresses, dateof birth, etc. The Subscriber Server 220 can in turn send a request toMedia Distribution Platform 230 to match the subscription datapertaining to the third-party subscriber against identificationinformation of a user of the Media Distribution Platform. Uponcompletion of a successful match between the third-party subscriber anda user of the Media Distribution Platform, Media Distribution Platform230 returns the matched user to the Subscriber Server 220. Returning amatched user allows the Subscriber Server 220 to send a request to MediaDistribution Platform 230 to grant a subscription to the publicationsubscribed to from Publisher 210. In some embodiments, granting asubscription to the publication can ultimately cause Media DistributionPlatform to unlock publication content currently stored in the MediaDistribution Platform for a given publisher and provide a user withaccess to the unlocked content. In some cases, despite the fact that amatched user was identified, the matched user's subscription toPublisher 210's publication may have expired. In this scenario, theSubscriber Server 220 can send a request to the Media DistributionPlatform to cancel a user's subscription to Publisher 210 publication.Provided that a subscription was granted to Publisher 210's publication,the method continues to Client 240 requesting the existing subscriptionmaterials from the Media Distribution Platform 230.

In some embodiments, although a user may indeed be a current subscriberto Publisher 210 publication, there are some situations in whichauthenticating a user's subscription might fail, thus causing MediaDistribution Platform 230 to send a failure message to Client 240. Somenon-limiting examples of scenarios in which authentication might failfor a subscriber include: the user has multiple billing addresses anddid not use the same address with Media Distribution Platform 230 thatthey used with the Publisher 210; there are multiple subscribers at asingle address; the user is not a subscriber; the publisher has pooraddress recognition; etc. In these failure cases additional informationmight be manually required from a user to authenticate a user'ssubscription. In some embodiments, a user interface will appear onClient 240 requesting fields a user needs to populate to authenticatethe user's subscription to publications. The user input received atClient 240 can be sent to Subscriber Server 220 to validate the userinput. Upon successful validation, Subscriber Server 220 can grant asubscription to Publisher 210's publication. Client 240 can subsequentlyreceive any newly-granted subscription from Media Distribution Platformand a subscription receipt can be sent from Media Distribution Platform230 to Client 240. In some embodiments, the subscription receiptreceived by Client 240 is accompanied by subscription publicationmaterials unlocked in Media Distribution Platform from Publisher 210 nowavailable for the user in digital format.

In some embodiments, a user can log into the media distribution platformserver by inputting their username or password into a user interfaceprovided on the media distribution platform. In some embodiments theusername and password can be an ID. In some embodiments, upon a userlogging into the media distribution platform, the media distributionplatform refreshes to identify new subscriptions available for downloadwhich are subscribed to by a user. If any new subscriptions availablefor download are identified, these subscriptions are included in thesubscriptions that are unlocked and provided to the media distributionplatform server.

FIG. 3 illustrates a method of automatically authenticating a user'ssubscription to non-digital media where publishers have not shared theirsubscription data with a media distribution platform. In some cases,publishers are unwilling to provide their subscription data to the mediadistribution platform. In this scenario, authenticating a user'ssubscriptions to publications occurs by authenticating a user'ssubscriptions directly with Publishers.

The method begins with Client 300 requesting a user's identificationinformation from Media Distribution Platform 315. Some non-limitingexamples of identification information are the subscriber's name, maidenname, home addresses, business addresses, mailing addresses, emailaddresses, date of birth, etc. As a non-limiting example, in FIG. 3Client 300 has requested a user's billing address from MediaDistribution Platform 315. The method continues to Media DistributionPlatform 315 returning the billing address to the Client 300. Uponreceipt the Client 300 can send the billing address to Third-PartyPublisher Server 310 to validate the billing address and authenticatethe user's subscriptions to publications from the Third-Party PublisherServer 310.

The method continues to Third-Party Publisher Server 310 returning anaccess token for each subscription authenticated from the Third-PartyPublisher. In some embodiments, one access token is provided to a userfor each subscription authenticated from the Third-Party Publisher. Forexample, if five publications are authenticated from Third-PartyPublisher Server 310, five access tokens are provided to the Client 300.In other embodiments, one universal access token is provided to a userfor all the subscriptions authenticated from Third-Party Publisherserver 310. For example, if five publications are authenticated fromThird-Party Publisher Server 310, one universal access token is providedto the Client 300.

In some instances, despite the fact that a user subscribes to one ormore publications from Third-Party Publisher Server 310, the process ofauthenticating the user's subscriptions might fail. Some non-limitingexamples of scenarios in which authentication might fail for asubscriber include: The user has multiple billing addresses and did notuse the same address with Media Distribution Platform 230 that they usedwith the Publisher 210; there are multiple subscribers at a singleaddress; the user is not a subscriber; the publisher has poor addressrecognition; etc. In these failure cases additional information can bemanually required from a user to authenticate a user's subscription. Insome embodiments, a user interface will appear on Client 300 requestingfields a user needs to populate to authenticate the user's subscriptionto publications. The user input received at Client 240 can be sent toThird-Party Publisher Server 310 to validate the user input. Uponsuccessful validation, Third-Party Publisher Server 310 returns anaccess token to Client 300. In some embodiments, one access token isprovided to a user for each subscription authenticated from thePublisher. For example, if five publications are authenticated fromThird-Party Publisher Server 310, five access tokens are provided to theClient 300. In other embodiments, one universal access token is providedto a user for all the subscriptions authenticated from Third-PartyPublisher server 310. For example, if five publications areauthenticated from Third-Party Publisher Server 310, one universalaccess token is provided to the Client 300.

The method continues with the Client 300 requesting content with theaccess token from the Content Server 305. In some embodiments, Client300 sends the access token to the Content server along with a requestfor content. In some embodiments, the access token for a givensubscription will be included with a request for content relating to asubscription from the publisher. This enables the Third-Party PublisherServer 310 to refuse the access token whenever the subscription isexpired or cancelled.

Upon receiving the access token, Content Server 305 sends the accesstoken to Third-Party Publisher Server 310 to validate the access token.Third-Party Publisher Server 310 validates the access token bydetermining that a user's subscription associated with the access tokenhas not expired or cancelled. Upon successful validation of the accesstoken, Third-Party Publisher Server 310 sends the validated access tokento the Content Server 305 which in turn allows the Content Server 305 toreturn content associated with the access token to Client 300.

In some embodiments, Third-Party Publisher Server contains the contentrequested by Client 300. Upon validation of the access token,Third-Party Publisher Server 310 returns the validated access token withsubscription content associated with the access token to the ContentServer 305. In other embodiments, Third-Party Publisher Server 310validates the access token and returns the validated access token toContent Server 305 which. Upon receipt of the access token, contentstored on the Content Server 305 is unlocked for distribution to theClient 300. Yet in another embodiment, Third-Party Publisher Server 310validates the access token and returns the validated access token toContent Server 305. Content associated with access token is stored inMedia Distribution Platform 315. Upon receipt of the validated accesstoken, Content Server 305 sends a request to Media Distribution Platform315 to unlock the content associated with the validated access token.Media Distribution Platform 315 in turn sends the requested content toClient 300.

In some embodiments, a user can log into the media distribution platformserver by inputting their username or password into a user interfaceprovided on the media distribution platform. In some embodiments theusername and password can be an ID. In some embodiments upon a userlogging into the media distribution platform, the media distributionplatform refreshes to identify new subscriptions available for downloadsubscribed to by a user. If any new subscriptions available for downloadare identified, these subscriptions are included in the subscriptionsthat are unlocked and provided to the media distribution platformserver.

FIG. 4 illustrates a method of automatically providing access to digitalversions of non-digital media a user subscribes to where thesubscription data is available to the media distribution platform. Inthis scenario, publishers have provided their subscription data to amedia distribution platform to allow for the authentication of a user'ssubscription to occur within the media distribution platform. As shown,the method begins at block 405 where a request is received for digitalversions of non-digital media subscribed to by a user. In someembodiments a user subscribes to a plurality of publications from aplurality of publishers. The request for digital versions of non-digitalmedia can involve one or more publications from a plurality ofpublishers. Additionally, the request for digital versions can occur asone input into a media distribution platform i.e. a click of a mouse, aninput on a touch screen of a graphical user interface of a mobiledevice, etc.

Upon receiving the request for digital versions, the method continues toblock 410 where user profile data corresponding to a media distributionplatform user account is received. The user profile data can includeidentification information. Some non-limiting examples of identificationinformation are the user's name, maiden name, home addresses, businessaddresses, mailing addresses, email addresses, date of birth, etc.

The method continues to block 415 where subscription data is receivedwhich corresponds to the user profile data. In some embodiments, thesubscription data can originate from a clearinghouse database containinga large majority of subscription data for multiple third-partysubscribers of a plurality of publishers. In other embodiments thesubscription data can originate from an API publishers use to providesubscription data to the media distribution platform server or theContent Server. Some non-limiting examples of subscription data are thesubscriber's name, maiden name, home addresses, business addresses,mailing addresses, email addresses, date of birth, etc.

Once the user profile data and subscription data are received the methodcontinues to block 420 where a data match is performed based on the userprofile data and the subscription data. In some embodiments thesubscription data and identification information are received at themedia distribution platform and the data match occurs at the mediadistribution platform server. In other embodiments the subscription dataand identification information are received at the Content Server andthe data match occurs at the Content Server. In either scenario, thedata match determines whether the user profile data and subscriptiondata refer to the same individual.

The method continues to block 425 where it is determined whether thedata match corresponds to a current non-digital media subscription. Insome embodiments the subscription data utilized to perform the datamatch may correspond to an expired or cancelled subscription. Therefore,determining whether or not the subscription data corresponds to acurrent subscription is critical step before providing digital versionsof non-digital media to the media distribution platform server or theContent Server.

Where the data match corresponds to a current non-digital mediasubscription, the method continues to step 430 where digital access tothe non-digital media subscription is provided to the media distributionplatform server or the Content Server. In some embodiments digitalversions of the non-digital media subscription can be accessed on themedia distribution server or a user's client device.

FIG. 5 illustrates a method of automatically providing access to digitalversions of non-digital media a user subscribes to where thesubscription data is private. In this scenario, publishers have electedto not provide their subscription data to a media distribution platformprecluding authentication of a user's subscription from occurring withinthe media distribution platform server. Rather, the authentication canoccur directly at the third-party publisher's server.

As shown, the method begins at block 505 where a request is received fordigital versions of non-digital media subscribed to by a user. In someembodiments a user subscribes to a plurality of publications from aplurality of publishers. The request for digital versions of non-digitalmedia can involve one or more publications from a plurality ofpublishers. Additionally, the request for digital versions can occur asone input into a media distribution platform, i.e., a click of a mouse,an input on a touch screen of a graphical user interface of a mobiledevice, etc.

The method continues to block 510 where user profile data correspondingto a media distribution platform user account is received. The userprofile data can include identification information. Some non-limitingexamples of identification information are the user's name, maiden name,home addresses, business addresses, mailing addresses, email addresses,date of birth, etc.

Upon receipt of the user profile data, the method continues to block 515where the user profile data received is sent to a third-party publisherto authenticate subscription to a non-digital media. In someembodiments, the portions of user profile data required to authenticatethe subscriptions vary by publisher. The media distribution platform candetermine which user profile data is required by the publisher, selectthe applicable portions of the user profile data and send those portionsto authenticate the subscription.

Provided the Publisher recognizes the user profile data sent, the methodcontinues to step 520 where an access token for a non-digital mediasubscription is received from the Publisher. In some embodiments, theaccess token for a given subscription will be included whenever the userreceives digital content relating to the subscription from thepublisher. This enables the publisher to refuse the access tokenwhenever the subscription is expired or cancelled. In some embodiments,one access token is provided to a user for each subscriptionauthenticated from the Publisher. For example, if five publications areauthenticated from Publisher, five access tokens are provided. In otherembodiments, one universal access token is provided to a user for allthe subscriptions authenticated from the Publisher. For example, if fivepublications are authenticated from the Publisher, one universal accesstoken is provided. In some embodiments the access token is received bythe media distribution platform server. In other embodiments the accesstoken is received by the client device.

The method continues to block 525 where the digital access to thenon-digital media subscription is requested from the Publisher includingthe access token. In some embodiments, a request is a request is sent tothe Publisher from the media distribution platform server or the clientdevice. The access token can accompany the request to enable thePublisher to identify the subscription requested and determine whetheror not the subscription is current, expired, or cancelled.

Where the access token is successfully verified by the Publisher, themethod continues to step 530 where digital access to the non-digitalmedia subscription is provided to the media distribution platform serveror the Content Server. In some embodiments digital versions of thenon-digital media subscription can be accessed on the media distributionserver or a user's client device.

FIG. 6 illustrates a method of providing access to digital versions ofnon-digital media a user subscribes to where the subscription data isavailable to the media distribution platform. In FIG. 6 a failure inauthenticating a subscription has occurred requiring manual user inputby a user. In these failure cases additional information can be manuallyrequired from a user to authenticate a user's subscription. In someembodiments, a user interface will appear on a client device requestingfields a user needs to populate to authenticate the user's subscriptionto publications. Where subscription data is available to the mediadistribution platform, the user input received at the client device canbe matched up against the subscription data, and if the input isrecognized, the user will be granted a subscription to digital content.

As shown, the method begins at block 605 where a failure has occurred inauthenticating a subscription to a publication. Despite the fact thatthe user may indeed be subscribed to the publication, the authenticationmight fail for multiple reasons. Some non-limiting examples of scenariosin which authentication might fail for a subscriber include: the userhas multiple billing addresses and did not use the same address with themedia distribution platform server that they used with the Publisher;there are multiple subscribers at a single address; the user is not asubscriber; the publisher has poor address recognition; etc.

The method continues to block 610 where inputs in a user interfacecorresponding to the subscription data available is received. In someembodiments, the subscription data available will dictate which inputfields are presented to the user. Some non-limiting examples of inputfields presented to the user are: mailing address, subscription accountnumber, email address, subscriber's name, maiden name, home addresses,business addresses, mailing addresses, email addresses, date of birth,username and password, etc.

Upon receipt of the inputs, the method continues to block 615 where theinputs received are matched against the subscription data available. Insome embodiments, the subscription data can be stored at the mediadistribution platform server. In other embodiments the subscription datacan be stored at the Content Server. In some instances the data matchingcan occur on the media distribution platform or the Content Server.

Where the matching of inputs received against available subscriptiondata is successful, the method continues to step 620 where digitalaccess to the non-digital media subscription is provided to the mediadistribution platform server or the Content Server. In some embodimentsdigital versions of the non-digital media subscription can be accessedon the media distribution server or a user's client device.

FIG. 7 illustrates a method of providing access to digital versions ofnon-digital media a user subscribes to where the subscription data isprivate. In FIG. 7 a failure in authenticating a subscription hasoccurred requiring manual user input by a user. In these failure casesadditional information can be manually required from a user toauthenticate a user's subscription. In some embodiments, a userinterface will appear on a client device requesting fields a user needsto populate to authenticate the user's subscription to publications.Where subscription data is private, the user input received at theclient device can be matched up against the subscription data, and ifthe input is recognized, the user will be granted a subscription todigital content.

As shown, the method begins at block 705 where a failure has occurred inauthenticating a subscription to a publication. Despite the fact thatthe user may indeed be subscribed to the publication, the authenticationmight fail for multiple reasons. Some non-limiting examples of scenariosin which authentication might fail for a subscriber include: the userhas multiple billing addresses and did not use the same address with themedia distribution platform server that they used with the Publisher;there are multiple subscribers at a single address; the user is not asubscriber; the publisher has poor address recognition; etc.

The method continues to block 710 where inputs in a user interfacerequested by a publisher to authenticate a subscription are received. Insome embodiments, the Publisher dictates which fields are presented tothe user. Some non-limiting examples of input fields presented to theuser are: mailing address, subscription account number, email address,subscriber's name, maiden name, home addresses, business addresses,mailing addresses, email addresses, date of birth, username andpassword, etc.

Upon receipt of the inputs, the method continues to block 715 where theinputs received are sent to the Publisher to authenticate thesubscription. Provided that the publisher recognizes the user inputs andis able to authenticate the subscription associated with the userinputs, the method continues to block 720 where an access token for asubscription is received from the Publisher for the given subscription.In some embodiments, the access token for a given subscription will beincluded whenever the user receives digital content relating to thesubscription from the publisher. This enables the publisher to refusethe access token whenever the subscription is expired or cancelled. Insome embodiments the access token can be received at the client device.In other embodiments the access token can be received at the mediadistribution platform server or the Content Server.

The method continues to block 725 where digital access to thenon-digital media subscription from the publisher using the access tokenis requested. In some embodiments a request for digital access can besent to the publisher including the access token. Thereafter, thepublisher can verify that the access token is not expired or cancelled.Provided that the access token is verified as relating to a currentsubscription, the method continues to block 730 where digital access tothe non-digital media subscription is provided to the media distributionplatform server or the Content Server. In some embodiments digitalversions of the non-digital media subscription can be accessed on themedia distribution server or a user's client device.

FIG. 8 illustrates an example flowchart of how a user's subscription toa non-digital media is authenticated and how digital versions of thenon-digital media are a provided. The flowchart begins at step 805 wherea request for digital versions of non-digital media subscriptions isreceived. The flowchart continues to step 810 where user profile data isreceived corresponding to a media distribution platform user account. Atstep 815, if the Publisher has shared subscription data with the mediadistribution platform the flowchart continues to step 840 where a datamatch is performed on the user profile data and subscription data. Theflowchart continues to step 845 which determines whether authenticationof the user's subscription to a non-digital media failed. If theauthentication was successful the flowchart continues to step 850 whereone or more non-digital media offered by the Publisher are determined tobe associated with the subscriber identified in the successful datamatch. The flowchart continues to step 875 where digital versions of thenon-digital media subscriptions are provided to the user.

Returning to step 845 where authentication of the subscriber has failedin the data match, the flowchart continues to step 855 where manual userinputs are received in a user interface. In some embodiments the manualuser inputs required are fields consistent with the subscription dataavailable. The flowchart continues to step 860 where the manual userinputs are matched against the subscription data available. Providedthat a successful data match occurs at step 860, the flowchart continuesto step 875 where digital versions of the non-digital mediasubscriptions are provided to the subscriber.

Returning to step 815, if the Publisher has not chosen to sharesubscription data the flowchart continues to step 820 where the userprofile data received is automatically sent directly to the Publisherabsent any user input. The flowchart continues at step 825 whereauthentication of a user subscription associated with the user profiledata is determined. Provided that the Publisher recognizes the userprofile data received and authentication of the users subscription tonon-digital media was successful, the flowchart continues to step 830where an access token is received from the Publisher. If anauthentication of a user's subscription to non-digital media fails atstep 825 the flowchart continues to step 865 where a user manuallyprovides inputs into a user interface requested by the publisher. Theflowchart continues to step 870 where the input manually provided by theuser are sent to the Publisher to authenticate the user's subscriptionto non-digital media materials.

In either scenario following step 825 where authentication wasautomatically successful or required manual user inputs to authenticatethe users subscription, the flowchart continues to step 830 where anaccess token is received from the Publisher. The flowchart continues to835 where a request for digital versions of the non-digital mediaauthenticated and the access token is sent to the Publisher. Theflowchart continues to step 875 where digital versions of thenon-digital media subscriptions are provided to the user.

FIG. 9A, and FIG. 9B illustrate exemplary possible system embodiments.The more appropriate embodiment will be apparent to those of ordinaryskill in the art when practicing the present technology. Persons ofordinary skill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 9A illustrates a conventional system bus computing systemarchitecture 900 wherein the components of the system are in electricalcommunication with each other using a bus 905. Exemplary system 900includes a processing unit (CPU or processor) 910 and a system bus 905that couples various system components including the system memory 915,such as read only memory (ROM) 920 and random access memory (RAM) 925,to the processor 910. The system 900 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 910. The system 900 can copy data from the memory915 and/or the storage device 930 to the cache 912 for quick access bythe processor 910. In this way, the cache can provide a performanceboost that avoids processor 910 delays while waiting for data. These andother modules can control or be configured to control the processor 910to perform various actions. Other system memory 915 may be available foruse as well. The memory 915 can include multiple different types ofmemory with different performance characteristics. The processor 910 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 932, module 2 934, and module 3 936 stored instorage device 930, configured to control the processor 910 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 910 can essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 900, an inputdevice 945 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 935 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 900. The communications interface940 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here can easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 930 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 925, read only memory (ROM) 920, andhybrids thereof.

The storage device 930 can include software modules 932, 934, 936 forcontrolling the processor 910. Other hardware or software modules arecontemplated. The storage device 930 can be connected to the system bus905. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 910, bus 905, display 935, and soforth, to carry out the function.

FIG. 9B illustrates a computer system 950 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 950 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 950 can include a processor955, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 955 cancommunicate with a chipset 960 that can control input to and output fromprocessor 955. In this example, chipset 960 outputs information tooutput 965, such as a display, and can read and write information tostorage device 970, which can include magnetic media, and solid statemedia, for example. Chipset 960 can also read data from and write datato RAM 975. A bridge 980 for interfacing with a variety of userinterface components 985 can be provided for interfacing with chipset960. Such user interface components 985 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 950 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 960 can also interface with one or more communication interfaces590 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 955 analyzing data stored in storage 970 or 975.Further, the machine can receive inputs from a user via user interfacecomponents 985 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 955.

It can be appreciated that exemplary systems 900 and 950 can have morethan one processor 910 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology canbe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions can be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that can be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1. A method comprising: receiving, at a media distribution platform, arequest for digital versions of non-digital media currently subscribedto by a user; obtaining profile data corresponding to a mediadistribution platform user account identifying the user, the profiledata stored in a database maintained at the media distribution platform;receiving subscription data from a clearinghouse database containingnon-digital media subscription data for a third-party publisher;transmitting the profile data to the clearing house database, theclearinghouse database including records of subscribers to non-digitalmedia; matching the profile data with the subscription data; and upon asuccessful match, providing a digital version of the non-digital mediasubscription on the media distribution platform after receiving anaccess token for the non-digital access to the non-digital mediasubscription from the third-party publisher based on the access token.2. The method of claim 1, wherein the matching occurs within the mediadistribution platform.
 3. The method of claim 1 further comprising:signing into the media distribution platform with a user login andpassword; and receiving one input into the media distribution platformto request the digital versions of non-digital media currentlysubscribed to by the user.
 4. The method of claim 2, wherein the oneinput into the media distribution platform is an input on a touch screenof a graphical user interface of a mobile device.
 5. The method of claim1 further comprising: refreshing digital versions of non-digital mediaavailable upon a user logging into the media distribution platform. 6.The method of claim 1 further comprising: providing digital versions ofa plurality of non-digital media subscriptions offered by a singlethird-party publisher on the media distribution platform.
 7. The methodof claim 1 further comprising: receiving a notification thatauthentication of a subscription to a non-digital media has failed;receiving inputs into a user interface on a media distribution platform,the input consisting of fields corresponding to the subscription dataavailable on the media distribution platform; performing a data matchbetween the inputs and the subscription data; determining whether thedata match corresponds to a current non-digital media subscription; andproviding digital versions of the non-digital media subscription on themedia distribution platform.
 8. (canceled)
 9. (canceled)
 10. (canceled)11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. Anon-transitory computer-readable storage medium having stored thereininstructions which, when executed by a processor, cause the processor toperform operations comprising: receive, at a media distributionplatform, a request for digital versions of non-digital media currentlysubscribed to by a user; obtain profile data corresponding to a mediadistribution platform user account identifying the user, the profiledata stored in a database maintained at the media distribution platform;receive subscription data corresponding to the profile data from aclearinghouse database containing subscription data for a third-partypublisher; transmit the profile data to the clearing house database, theclearinghouse database including records of subscribers to non-digitalmedia; perform a data match based on the profile data and thesubscription data; determine whether the data match corresponds to anon-digital media subscription; and upon a successful match, providedigital versions of the non-digital media subscription on the mediadistribution platform after receiving an access token for thenon-digital access to the non-digital media subscription from thethird-party publisher based on the access token.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the instructions furthercauser the processor to: sign into the media distribution platform witha user login and password; and receive one input into the mediadistribution platform to request the digital versions of non-digitalmedia currently subscribed to by the user.
 17. The non-transitorycomputer-readable medium of claim 16, wherein the one input into themedia distribution platform is an input on a touch screen of a graphicaluser interface of a mobile device.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the instructions furthercauser the processor to: refresh digital versions of non-digital mediaavailable upon a user logging into the media distribution platform. 19.The non-transitory computer-readable medium of claim 15, wherein theinstructions further causer the processor to: provide digital versionsof a plurality of non-digital media subscriptions offered by a singlethird-party publisher on the media distribution platform.
 20. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions further causer the processor to: receive a notificationthat authentication of a subscription to a non-digital media has failed;receive inputs into a user interface on a media distribution platform,the input consisting of fields corresponding to the subscription dataavailable on the media distribution platform; perform a data matchbetween the inputs and the subscription data; determine whether the datamatch corresponds to a current non-digital media subscription; andprovide digital versions of the non-digital media subscription on themedia distribution platform.
 21. (canceled)
 22. (canceled) 23.(canceled)
 24. (canceled)
 25. (canceled)
 26. A method comprising:receiving, at a media distribution platform, a request for digitalversions of non-digital media currently subscribed to by a user;obtaining profile data corresponding to a media distribution platformuser account corresponding to the user, the profile data stored in adatabase maintained at the media distribution platform; receivingsubscription data from a clearinghouse database including records ofsubscribers to non-digital media provided by a third-party publisher;matching the profile data with the subscription data; and upon asuccessful match, providing a digital version of the non-digital mediasubscription on the media distribution platform after receiving anaccess token for the non-digital access to the non-digital mediasubscription from the third-party publisher based on the access token.